Skip to main content

Setting up the API v2

Before you start integration, you need to get the following information from us:

  • API_URL – the URL to get access to the API;
  • clientKey – a unique identifier of your integration. It is used to associate API requests with your account;
  • SECRET_KEY – the secret key used to sign requests. The secret key is configured specifically for each clientKey.

Setting Up Authorization for Native Applications​

If you are going to use our native client applications, you will need to provide a URL to the user authentication page. This page should contain the login form with the Login and Cancel buttons. If a user clicks “Cancel”, a special URL poker://on-close should be used.

When a user clicks “Login”, the following operations should be executed:

  • user authorization in your system
  • if the authorization was successful, a session should be created through our API. It is also necessary to pass “internal” as the authType parameter value.
  • after that, the user should be redirected to the redirect_url that is received in response after the session was created.

The login page design should be adjusted to mobile devices and correctly open for the following sizes:

  • desktop: 340х210
  • tablet (resolution1024х768): 558х610
  • mobile (resolution 640х1136): 610х610